ASP.NET

We used ASP.NET to design our product which handles the energy-related functionality. In same product, we almost created 5000 displays that are interrelated and handle the end-to-end processes. we had created multiple displays which handle reporting, entry pages, summary pages, etc. Product which we created using ASP is in the market nowadays and solving energy-related problems .

We are currently implementing a few microservices with .NET 6 for our internal operations. It’s very fast, seems quite reliable, has a huge community. It’s also multiplatform in ways, so we can potentially reuse some logic in future applications

We use ASP.NET for our internal applications, and since all of our other applications and infrastructure is already prepared for ASP.NET applications, the implementation of the said apps is streamlined and fast. It works great for complex operations, back-end performance is outstanding. The front-end development is very reliable but not modern. If you want something to reliably work and don't mind the clunkyness of front-end, that's great.

When we need to create a fast web portal for our customers with small integration with a database, the simplest way is to use ASP.NET. We can put some code frontend to be quickly accessed but the customer. In the other hand, we can officiate the complexity of some functions into the backend.

ASP.NET is considered to be the best framework. We typically use it across all of our web projects and in our organization because it is a programming language that allows us to create web-based sites or applications. ASP.NET creates websites based on CSS, HTML5, and JavaScript that are smooth, fast, and scale for many users. It is a well-established web platform that can build enterprise-class server-based applications for Windows. ASP.NET's MVC is the framework of choice for most of the websites we build and integrate it with our projects with various systems. In terms of web page development, ASP.NET is the fastest. Instead of sending a request to the server every time, pages are safer and quicker. We need a few lines of code because so many things can be dragged and dropped. Because of its developer friendliness and versatility, ASP.NET is a popular choice.

ASP.NET is used for virtually every system developed and in use at my organisation, specifically MVC and webforms. It is used across the entire organisation for internal and external applications. It addresses the need to rapidly develop web-based systems to a pre-defined programming model that is proven to work (such as MVC) and have those systems be maintainable. It was a huge step forward, especially when ASP.NET MVC was released. However, when I compare it to even more modern technology, such as Express for NodeJS - it just gets too complicated too quickly. Express manages to accomplish the exact same functionality but in a very simple and succinct way. ASP.NET, as with all .NET based development, tends to get unnecessarily complicated quickly.

ASP.NET is being used throughout my organization for the development of both windows and desktop applications. Custom tools are being created by it to ease out our processes and client-side applications are also developed on it. Further, it could be connected to a backend like SQL Server and a Full-stack development can be easily done on it.

We use ASP.Net to build a wide variety of applications for our customers. We have built simple "marketing" style websites with a simple contact form built in. We have also built full scale application tracking applications that integrate with numerous external systems and have a mini document management system that integrates with Amazon S3. ASP.Net provides a robust framework of features that allows us to develop quickly and efficiently. With the numerous libraries available, we can easily extend our needs without having to reinvent the wheel.

ASP.NET is used throughout the upper levels of our Information Technology group. Lower levels and the rest of the company remains limited to VBA via Excel, Access, etc. due to security restrictions set by the company. ASP.NET addresses the more complex business problems, especially web integration, which cannot be addressed with the simpler tools. We also use ASP.NET to allow various back-end databases (Oracle, SQL, etc.) to communicate to a main program or even mobile devices.

It was used by our front-end development team. We served web pages for the company's free tier solution, which needed SEO, so it had to be server rendered. The business logic layer was already build on top of .NET so it made sense to stick to the same tech stack.

Personally I started my career with ASP.NET before MVC arrived. The old ASP.NET tried to abstract the web environment which ended up complicating things and misleading young developers. ASP.NET and Microsoft in general have since greatly mended their ways and although it's not my go-to stack, ASP.NET MVC is a completely legitimate one.

We use ASP.net across the whole organization and all products.

We write multiple software products across our teams. The majority of these products are written in some version of ASP.NET. It is used daily for development, debugging, and all other R&D activities. This is across multiple versions of .NET and both legacy applications and new greenfield applications. In general, all back-end code is .NET.